pf-status-relay-operator: FBC migration and operator log capture#79044
pf-status-relay-operator: FBC migration and operator log capture#79044karampok wants to merge 2 commits intoopenshift:mainfrom
Conversation
ci-operator emits deprecation warning: WARN: Building index images is deprecated and will be removed from ci-operator soon. See https://docs.ci.openshift.org/how-tos/ testing-operator-sdk-operators/#moving-to-file-based-catalog Fix: add skip_building_index: true to operator bundle definition. ci-index-operator-bundle job replaced by ci-bundle-operator-bundle which builds the bundle directly without generating an index image. e2e-validation already uses OO_BUNDLE so no test changes needed. Assisted-By: Claude
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: karampok The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/pj-rehearse |
|
@karampok: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughUpdates the OpenShift CI config for pf-status-relay-operator: sets ChangesCI Pipeline Configuration
Estimated Code Review Effort🎯 2 (Simple) | ⏱️ ~8 minutes 🚥 Pre-merge checks | ✅ 12✅ Passed checks (12 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Operator pod logs were not preserved in CI artifacts. gather-extra collects all-namespaces but the operator namespace is cleaned up before collection reaches it, leaving the artifact directory empty. Fix: dump controller-manager logs to ARTIFACT_DIR at end of e2e-test step after deployment is confirmed Available. Logs are uploaded to GCS automatically and available in the job artifacts. Assisted-By: Claude
0e9ff83 to
b3d723f
Compare
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse |
|
@karampok: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@karampok: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary
Migrate operator bundle to file-based catalog by adding
skip_building_index: true, resolving deprecation warning emitted by ci-operator:The
ci-index-operator-bundlepresubmit is replaced byci-bundle-operator-bundle. Thee2e-validationtest already usesOO_BUNDLEso no test changes are needed.Capture controller-manager logs in
e2e-validationartifacts. Operator pod logs were absent from CI artifacts because the namespace is cleaned up beforegather-extracollection reaches it. Logs are now dumped toARTIFACT_DIRafter the deployment is confirmed Available.Test plan
ci-bundle-operator-bundlepresubmit passes (replacesci-index-operator-bundle)e2e-validationpasses andoperator-controller-manager.logappears in artifactsSummary by CodeRabbit